Fix span logs and tags while logging with level ERROR - #328
Conversation
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (18)
Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review. WalkthroughChangesThe pull request updates copyright years across project files, changes the AOP parent version to Spring Cloud update
Merge Risk: ⚪ Minimal · up to This PR makes a localized correction to span error logging and tagging; no actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
While using SpanLogsAppender, we found that while logging with level ERROR, the span log event's value is something like io.opentracing.tag.BooleanTag@7251412f. So i search the behavior of other components(e.g. io.opentracing.contrib.jdbc.JdbcTracingUtils.onError), and found that we should log Tag.ERROR.getKey() instead of Tag.ERROR, and tag error.
Summary by CodeRabbit
Bug Fixes
Chores